Programming Assignment Policies

1 Collaboration

You must work on programming assignments entirely on your own. You may only request help on programming assignments from the course instructor or the lab assistant (if there is one). If you receive such help you must make note of it in the documentation for the relevant class(es).

You may request help on general topics from other students and friends. However, when doing so you must never refer to the programming assignment, either directly or indirectly. This means that, when asking for general help, you may not refer to the description of the programming assignment, code written for the assignment, errors generated by compiling or running code written for the assignment, or the output generated by running code written for the assignment.

2 Submission

Except when otherwise noted, this course uses a two-part submission process.

You must demonstrate that your code builds and executes properly using an electronic submission system.
You must submit "hardcopy" of the code (properly documented) on 8.5"x11.0" paper.

Details are provided below.

2.1 Electronic Submission

You must submit your code electronically using SUBMIT. You will be notified immediately if your submission fails to pass the tests.

If your submission fails to pass the required tests then you have not successfully submitted your code electronically. You must then review your code to determine the source of the problem(s) and correct it (them). In some cases, the submission report generated by SUBMIT will provide information about the tests. In other cases it will not (intentionally). If it does not, it is your responsibility to identify the symptom(s) and find the fault(s) using test cases of your own.

2.2 Hardcopy Submission

You may not submit hardcopy unless and until you successfully submit your code electronically. You must submit the hardcopy within three official meetings (either lecture or lab) of the electronic submission. For example, if you successfully submit electronically on Monday night then your hardcopy is due in class on Thursday.

You must submit a hardcopy of the .pdf file that was generated by SUBMIT.

The hardcopy submission must be stapled in the upper left-hand corner.

All code and documentation written for the programming assignments must conform to the course style guides.

You must also keep an electronic copy of the code exactly as it was tested. You may be asked to submit this electronic copy as well.

3 Grading

Solutions to programming assignments will be graded on a 100-point scale (i.e., the minimum possible grade is 0 and the maximum possible grade is 100). Points will be deducted for a variety of reasons, including: failing the tests conducted as part of the electronic submission process, failing to conform to the course style guide, failing to be properly documented, poor design, poor implementation, and inelegance.

There are several particularly important grading policies that you should be aware of:

No submissions will be accepted more than one week after the due date (i.e., you will receive a grade of 0 on an assignment that is one week or more late).
There is a 5 point deduction fo the first "business day" (or part thereof) that your electronic submission is late, and a 10 point deduction for each subsequent "business day" (or part thereof) that your electronic submission is late.
There is a 25 point deduction for submissions that do not conform to the course style guide(s) and/or submission requirements.
There is a 100 point deduction for submissions that do not pass the tests conducted during the submit process.

If you violate the University's Honor Code (at any time) you will receive a grade of F for the course, other penalties may be imposed, and the violation will be reported to the Honor Council.